home *** CD-ROM | disk | FTP | other *** search
- I finally took some time to read the IMSP specification. Here are some
- comments:
-
- 1) Should the wildcard syntax used by FIND be limited to the TOPS-20 wildcard
- characters selected by IMAP2? Perhaps a regular expression syntax would be
- better??
-
- 2) I like the way IMSP deals with server names in FIND results. Much better
- than IMAP2. However, there's one additional improvement to be made, which
- is to include the pattern in the results. For example:
- a002 FIND MAILBOXES *
- * MAILBOX * INBOX (imap1.podunk.edu)
- * MAILBOX * FOOBAR (imap23.podunk.edu)
- a002 OK FIND completed
- This will greatly please certain people, and there's no harm done by doing
- it now. Some of the other commands which return data should also have the
- request patterns included in the responses.
-
- 3) I like FIND UNSEEN.MAILBOXES and FIND UNSEEN.BBOARDS -- neat idea and a
- possible big performance win.
-
- 4) I don't think you need to justify your selection of a list of server hosts
- for FIND instead of using the {host} syntax. The {host} syntax is
- obviously inappropriate for this purpose.
-
- 5) Why not fix the ``design flaw'' by requiring that FIND ALL.mumble indicate
- subscription status. You don't have to be bug-for-bug matching with IMAP.
-
- 6) I'm not sure I like the proposed implementation of FIND UNSEEN.mumble,
- since it seems to preclude doing it by hunt/examination. This should be a
- implementation detail and not a protocol detail.
-
- 7) Instead of CREATE and CREATE.BBOARD, I suggest CREATE MAILBOX and
- CREATE BBOARD & etc. for the other commands.
-
- 8) I'm not convinced that a user's private address book couldn't be part of
- the GET/SET stuff instead of having to wait for directory services.
-
-
-
-